Add row-lineage support with Spark tests - #3972
Draft
rambleraptor wants to merge 2 commits into
Draft
rambleraptor wants to merge 2 commits into
rambleraptor wants to merge 2 commits into
Conversation
This ensures that row lineage values are updated.
rambleraptor
marked this pull request as draft
September 15, 2026 20:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this change
We've got several differing versions of this baked into several PRs at this point. I wanted to split it out to help make reviewing easier.
This builds out support for incrementing
next-row-idvalues and gets row lineage all wired up.AI Disclosure: Claude helped write the code under my supervision. I specified the testing plan that I wanted to see.
Are these changes tested?
Includes unit and Spark test
Are there any user-facing changes?